Tom,

Yup, it sure is. Well, there's at least a full day of my time, and a bunch of material, wasted....

I am seeing another problem that is rather alarming, to say the least. Today it nearly cost me a good test indicator. I am still seeing occasional position loss, and even servo faults, when jogging with the pendant. I've just discovered that this seems to only happen AFTER running G-code. In addition, the machine will make un-commanded moves when I do an MDI. This too seems to happen only AFTER running G-code. There must be something I'm doing wrong in stopping the interpreter. Here's an example of something I can reproduce with some consistency:

Start a G-code program
Pause the program with FeedHold
Stop the program with Stop
If I now jog, particularly using MoveExp, I will experience either a small position loss, or a servo fault, often at VERY low jog speeds. It seems to happen mostly on a reverse in direction, and I can hear the servo make a loud "bang" when it happens, so it must be getting a really bogus command.
If, after jogging, I do an MDI command, it will move BOTH the axis commanded by the MDI command, AND the one that was previously jogged! The axis that was jogged seems to want to take off somewhere very far away, and I have to hit E-Stop to kill the move. So, for example, if I jog the X axis, then MDI "G0 Z1", The Z axis will make the correct move, the X axis will take off at rapid speed for who-knows-where, and just keep on going.

My FeedHold button does this:

String s = KMController.WriteLineReadLine("GetStopState");
if (s.Equals("0"))
{
KMController.WriteLine("StopImmediate0");
FeedHoldIsOn = true;
} else {
KMController.WriteLine("StopImmediate1");
FeedHoldIsOn = false;
}

My Stop button does this:

KMController.Interpreter.Halt();

What am I missing? How do I make sure the Interpreter has completely flushed any pending moves?

Regards,
Ray L.

--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Ray,
>  
> Hmmm...  Looks like the documentation is wrong.  I think the default is to pulse low.  Setting bit7 reverses the polarity to pulse high.
>  
> Regards
> TK
>  
>  
>
> From: himykabibble <jagboy@...>
> To: DynoMotion@yahoogroups.com
> Sent: Saturday, February 18, 2012 12:54 PM
> Subject: [DynoMotion] Re: Setting Step Polarity Low....
>
>
>  
> Tom,
>
> I will try writing a different value, but writing 32 + 0x80, should I not see a 2 uSec wide LOW pulse?
>
> Regards,
> Ray L.
>
> --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> >
> > Hi Ray,
> >  
> > The value of 32 is what sets the 2us.  To change to 4us (actually 3.78us) change the 32 to the max allowed value of 63.
> >  
> > The FPGA remembers the last setting forever (or until a power cycle).  So are you adding and removing bit7 (0x80)?  Or are you just not writing anything and expecting a change?  Try:
> >  
> > FPGA(STEP_PULSE_LENGTH_ADD) = 63 + 0x80;
> >
> > and
> >  
> > FPGA(STEP_PULSE_LENGTH_ADD) = 63;
> >
> > and see what you get.
> >  
> > Reagrds
> > TK
> >  
> >
> > From: himykabibble <jagboy@>
> > To: DynoMotion@yahoogroups.com
> > Sent: Saturday, February 18, 2012 12:00 PM
> > Subject: [DynoMotion] Setting Step Polarity Low....
> >
> >
> >  
> > I'm on the trail of what I hope will be the last problem.... I'm finding I have a small position loss on the Z axis, after many moves. After doing a sequence of several hundred rapid moves over distances ranging from 0.1"-3", I have a very consistent offset of about +0.0025". Since I *never* once had a position loss with the SmoothStepper, and the loss is still there even with the axis massively de-tuned, it seems to me this HAS to be an electrical problem. So, I broke out the o-scope, and looked at the step signal, and was surprised to find that no matter whether I select high or low polarity, the step pulse looks exactly the same - a 2uSec wide high pulse. I am setting the polarity in my Init.c, using this line, copied from the documentation:
> >
> > // set the pulse time to ~ 2us and pulse the Step low
> > FPGA(STEP_PULSE_LENGTH_ADD) = 32 + 0x80;
> >
> > Why does this have no effect?
> >
> > Regards,
> > Ray L.
> >
>

Tom,

Any comments on my interpreter problem below?

Regards,
Ray L.

--- In DynoMotion@yahoogroups.com, "himykabibble" <jagboy@...> wrote:
>
> Tom,
>
> Yup, it sure is. Well, there's at least a full day of my time, and a bunch of material, wasted....
>
> I am seeing another problem that is rather alarming, to say the least. Today it nearly cost me a good test indicator. I am still seeing occasional position loss, and even servo faults, when jogging with the pendant. I've just discovered that this seems to only happen AFTER running G-code. In addition, the machine will make un-commanded moves when I do an MDI. This too seems to happen only AFTER running G-code. There must be something I'm doing wrong in stopping the interpreter. Here's an example of something I can reproduce with some consistency:
>
> Start a G-code program
> Pause the program with FeedHold
> Stop the program with Stop
> If I now jog, particularly using MoveExp, I will experience either a small position loss, or a servo fault, often at VERY low jog speeds. It seems to happen mostly on a reverse in direction, and I can hear the servo make a loud "bang" when it happens, so it must be getting a really bogus command.
> If, after jogging, I do an MDI command, it will move BOTH the axis commanded by the MDI command, AND the one that was previously jogged! The axis that was jogged seems to want to take off somewhere very far away, and I have to hit E-Stop to kill the move. So, for example, if I jog the X axis, then MDI "G0 Z1", The Z axis will make the correct move, the X axis will take off at rapid speed for who-knows-where, and just keep on going.
>
> My FeedHold button does this:
>
> String s = KMController.WriteLineReadLine("GetStopState");
> if (s.Equals("0"))
> {
> KMController.WriteLine("StopImmediate0");
> FeedHoldIsOn = true;
> } else {
> KMController.WriteLine("StopImmediate1");
> FeedHoldIsOn = false;
> }
>
> My Stop button does this:
>
> KMController.Interpreter.Halt();
>
> What am I missing? How do I make sure the Interpreter has completely flushed any pending moves?
>
> Regards,
> Ray L.
>
> --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> >
> > Hi Ray,
> >  
> > Hmmm...  Looks like the documentation is wrong.  I think the default is to pulse low.  Setting bit7 reverses the polarity to pulse high.
> >  
> > Regards
> > TK
> >  
> >  
> >
> > From: himykabibble <jagboy@>
> > To: DynoMotion@yahoogroups.com
> > Sent: Saturday, February 18, 2012 12:54 PM
> > Subject: [DynoMotion] Re: Setting Step Polarity Low....
> >
> >
> >  
> > Tom,
> >
> > I will try writing a different value, but writing 32 + 0x80, should I not see a 2 uSec wide LOW pulse?
> >
> > Regards,
> > Ray L.
> >
> > --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> > >
> > > Hi Ray,
> > >  
> > > The value of 32 is what sets the 2us.  To change to 4us (actually 3.78us) change the 32 to the max allowed value of 63.
> > >  
> > > The FPGA remembers the last setting forever (or until a power cycle).  So are you adding and removing bit7 (0x80)?  Or are you just not writing anything and expecting a change?  Try:
> > >  
> > > FPGA(STEP_PULSE_LENGTH_ADD) = 63 + 0x80;
> > >
> > > and
> > >  
> > > FPGA(STEP_PULSE_LENGTH_ADD) = 63;
> > >
> > > and see what you get.
> > >  
> > > Reagrds
> > > TK
> > >  
> > >
> > > From: himykabibble <jagboy@>
> > > To: DynoMotion@yahoogroups.com
> > > Sent: Saturday, February 18, 2012 12:00 PM
> > > Subject: [DynoMotion] Setting Step Polarity Low....
> > >
> > >
> > >  
> > > I'm on the trail of what I hope will be the last problem.... I'm finding I have a small position loss on the Z axis, after many moves. After doing a sequence of several hundred rapid moves over distances ranging from 0.1"-3", I have a very consistent offset of about +0.0025". Since I *never* once had a position loss with the SmoothStepper, and the loss is still there even with the axis massively de-tuned, it seems to me this HAS to be an electrical problem. So, I broke out the o-scope, and looked at the step signal, and was surprised to find that no matter whether I select high or low polarity, the step pulse looks exactly the same - a 2uSec wide high pulse. I am setting the polarity in my Init.c, using this line, copied from the documentation:
> > >
> > > // set the pulse time to ~ 2us and pulse the Step low
> > > FPGA(STEP_PULSE_LENGTH_ADD) = 32 + 0x80;
> > >
> > > Why does this have no effect?
> > >
> > > Regards,
> > > Ray L.
> > >
> >
>

Asking one more time....

--- In DynoMotion@yahoogroups.com, "himykabibble" <jagboy@...> wrote:
>
> Tom,
>
> Any comments on my interpreter problem below?
>
> Regards,
> Ray L.
>
> --- In DynoMotion@yahoogroups.com, "himykabibble" <jagboy@> wrote:
> >
> > Tom,
> >
> > Yup, it sure is. Well, there's at least a full day of my time, and a bunch of material, wasted....
> >
> > I am seeing another problem that is rather alarming, to say the least. Today it nearly cost me a good test indicator. I am still seeing occasional position loss, and even servo faults, when jogging with the pendant. I've just discovered that this seems to only happen AFTER running G-code. In addition, the machine will make un-commanded moves when I do an MDI. This too seems to happen only AFTER running G-code. There must be something I'm doing wrong in stopping the interpreter. Here's an example of something I can reproduce with some consistency:
> >
> > Start a G-code program
> > Pause the program with FeedHold
> > Stop the program with Stop
> > If I now jog, particularly using MoveExp, I will experience either a small position loss, or a servo fault, often at VERY low jog speeds. It seems to happen mostly on a reverse in direction, and I can hear the servo make a loud "bang" when it happens, so it must be getting a really bogus command.
> > If, after jogging, I do an MDI command, it will move BOTH the axis commanded by the MDI command, AND the one that was previously jogged! The axis that was jogged seems to want to take off somewhere very far away, and I have to hit E-Stop to kill the move. So, for example, if I jog the X axis, then MDI "G0 Z1", The Z axis will make the correct move, the X axis will take off at rapid speed for who-knows-where, and just keep on going.
> >
> > My FeedHold button does this:
> >
> > String s = KMController.WriteLineReadLine("GetStopState");
> > if (s.Equals("0"))
> > {
> > KMController.WriteLine("StopImmediate0");
> > FeedHoldIsOn = true;
> > } else {
> > KMController.WriteLine("StopImmediate1");
> > FeedHoldIsOn = false;
> > }
> >
> > My Stop button does this:
> >
> > KMController.Interpreter.Halt();
> >
> > What am I missing? How do I make sure the Interpreter has completely flushed any pending moves?
> >
> > Regards,
> > Ray L.
> >
> > --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> > >
> > > Hi Ray,
> > >  
> > > Hmmm...  Looks like the documentation is wrong.  I think the default is to pulse low.  Setting bit7 reverses the polarity to pulse high.
> > >  
> > > Regards
> > > TK
> > >  
> > >  
> > >
> > > From: himykabibble <jagboy@>
> > > To: DynoMotion@yahoogroups.com
> > > Sent: Saturday, February 18, 2012 12:54 PM
> > > Subject: [DynoMotion] Re: Setting Step Polarity Low....
> > >
> > >
> > >  
> > > Tom,
> > >
> > > I will try writing a different value, but writing 32 + 0x80, should I not see a 2 uSec wide LOW pulse?
> > >
> > > Regards,
> > > Ray L.
> > >
> > > --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > >
> > > > Hi Ray,
> > > >  
> > > > The value of 32 is what sets the 2us.  To change to 4us (actually 3.78us) change the 32 to the max allowed value of 63.
> > > >  
> > > > The FPGA remembers the last setting forever (or until a power cycle).  So are you adding and removing bit7 (0x80)?  Or are you just not writing anything and expecting a change?  Try:
> > > >  
> > > > FPGA(STEP_PULSE_LENGTH_ADD) = 63 + 0x80;
> > > >
> > > > and
> > > >  
> > > > FPGA(STEP_PULSE_LENGTH_ADD) = 63;
> > > >
> > > > and see what you get.
> > > >  
> > > > Reagrds
> > > > TK
> > > >  
> > > >
> > > > From: himykabibble <jagboy@>
> > > > To: DynoMotion@yahoogroups.com
> > > > Sent: Saturday, February 18, 2012 12:00 PM
> > > > Subject: [DynoMotion] Setting Step Polarity Low....
> > > >
> > > >
> > > >  
> > > > I'm on the trail of what I hope will be the last problem.... I'm finding I have a small position loss on the Z axis, after many moves. After doing a sequence of several hundred rapid moves over distances ranging from 0.1"-3", I have a very consistent offset of about +0.0025". Since I *never* once had a position loss with the SmoothStepper, and the loss is still there even with the axis massively de-tuned, it seems to me this HAS to be an electrical problem. So, I broke out the o-scope, and looked at the step signal, and was surprised to find that no matter whether I select high or low polarity, the step pulse looks exactly the same - a 2uSec wide high pulse. I am setting the polarity in my Init.c, using this line, copied from the documentation:
> > > >
> > > > // set the pulse time to ~ 2us and pulse the Step low
> > > > FPGA(STEP_PULSE_LENGTH_ADD) = 32 + 0x80;
> > > >
> > > > Why does this have no effect?
> > > >
> > > > Regards,
> > > > Ray L.
> > > >
> > >
> >
>